< previous page page_292 next page >

Page 292
Tasks that are queued per workgroup and role
Rolling back problem processes and tasks
Email and messaging facilities such as the Internet/intranet or Messaging Application Programming Interface (MAPI)
Assigning users to roles and workgroups
Tracking the costs and time delays associated with each task, totaled per role and workgroup
The order sequence for when one workgroup is dependent on another for the overall product to be delivered
How many workflow servers to have in operation at any given time in case one server goes down (threatening the workflow between workgroups)
Structuring workgroups and designing the flow of work between them involves lots of business rules and triggering events (which are conveniently supported in Visual Basic classes). In this lesson, I won't cover lots of business rules because a separate lesson, Day 15, The Business Rules Subsystem, deals with business rules. Here, you simply want to capture the basic mechanics of the interactions between workgroups and roles.
Each use case has a sequence of events associated with it. These sequences of events are, in effect, tasks. If you think about it, everything you do at work for which your employer is really paying you is in essence a part of a bigger workflow. Imagine for a moment that you've just been hired by an investment firm. The bank would have a process called Acclimate New Employee that has a sequence of events associated.
The investment firm uses a mix of manual and automated processes to process you in as a new employee. The hiring manager triggers the New Employee on Board event that routes forms related to 401(k) and other benefits to the Human Resources workgroup. In parallel (parallel routing), a message is sent to the Security workgroup so that an employee badge can be made for you upon your passing a background check. Also in parallel, the Information Services and Computer Security workgroup receives a form from the hiring manager with your personal information so that you can get authenticated to the proper computers and have an email account. By now, you probably get the picture. The general steps involved in a typical task within a workflow include the following:
Choose and start an associated task, which can include starting a software application.
Implement the work for that task, which can include creating one or more records or documents.
Delegate the work to the proper role or workgroup.

 
< previous page page_292 next page >

If you like this book, buy it!